feat: add Bug Report option & About menu in Settings, fix Windows onboarding path linking#72
Conversation
…oarding path linking
|
Warning Review limit reached
More reviews will be available in 9 minutes and 1 second. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (8)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Summary of Changes
onboarding\Editor.md), causing internal Markdown/filelinks inWelcome.mdto fail lookup and generate empty duplicate files. Normalized note IDs across the Rust backend (fs.rs) and TypeScript frontend (useNoteStorage.ts,markdownPlugin.ts,GraphView.tsx) to consistently use forward slashes on all platforms. Updated onboarding file logic to ensure templates regenerate cleanly on app updates.Verification & Testing
npm run lint(passed cleanly with Prettier & ESLint rules applied).npx vitest run(35/35 unit tests passed).npm run build(Vite + TypeScript production bundle generated cleanly).cargo check(Rust backend verified with no errors).